Open platform architecture for integrating multiple heterogeneous network functions

ABSTRACT

A platform for seamlessly hosts a plurality of disparate types of packet processing applications. One or more applications are loaded onto a service card on the platform. A programmable path structure is included that maps a logical path for processing of the packets through one or more of the plurality of service cards according to characteristics of the packets. Multiple path structures may be programmed into the platform to offer different service paths for different types of packets.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent application is related to the following U.S. PatentApplications, commonly assigned herewith: U.S. patent application Ser.No. 11/824,482 (U.S. Pat. No. 8,000,329), from which the presentapplication claims priority under 35 U.S.C. §120; U.S. patentapplication Ser. No. 11/824,555, entitled “NETWORK SYSTEM HAVING ANEXTENSIBLE CONTROL PLANE”; and U.S. patent application Ser. No.11/824,565 (U.S. Pat. No. 7,843,914), entitled “NETWORK SYSTEM HAVING ANEXTENSIBLE FORWARDING PLANE”. The contents of the aforementionedapplications and/or patents are fully incorporated herein by reference.

TECHNICAL FIELD

The present invention relates generally to networking, and morespecifically, to integrating different networking applications on asingle platform.

BACKGROUND

Edge devices provide packet connectivity entry points into a corenetwork. They typically control and analyze the flow of traffic enteringthe core network, provide security to the core network by preventingharmful traffic from entering it, or provide enhancements toapplications.

Examples of edge devices that monitor and analyze traffic, includetraffic monitoring systems, traffic analysis systems, flow replicationsystems, and various other systems that monitor and control the type oftraffic entering the core network.

Examples of edge devices that analyze the content of data entering thenetwork to provide security to the core network include firewalls anddetection/prevention equipment.

Briefly, a firewall refers to a device which limits access to a networkby only allowing authorized flows/users access to a private network.

Whereas, detection/prevention equipment refers to systems that identifyand block malicious code from entering a network, such as, but notlimited to: computer viruses, worms, trojan horses, spam, malware,spyware, adware, and other malicious and unwanted software. Intrusiondetection equipment may also include systems that detect when an attackis being perpetrated on a core network, such as a denial-of-serviceattack.

Examples of edge devices that provide enhancement of applicationsinclude applications that enhance the flow of packets, contentadaptation applications, and acceleration application functions.

In many instances companies and organizations will purchase thebest-in-class edge device solutions for use at the edge of a network.For example, an organization may purchase Vendor A's virus detectionproduct, Vendor's B firewall, Vendor's C flow replication product, andVendor's D router, because each is the best-in-class or for some otherreason.

As a result most devices found at the edge of a core network, are ahodgepodge of dissimilar interconnected devices each performing adifferent task. The total cost for setting-up and operating thesedisparate edge solutions is soaring out of control. Besides purchasingall these different solutions, there are costs associated with keepingthe equipment running, and managing software on all of the disparatepieces of equipment. Moreover, adding equipment to the edge of thenetwork to handle growing network demands is often complicated andinflexible.

Furthermore, with multiple types of equipment needed to examine packetsfor different purposes, such as malware, DDoS, firewalls, routing, andso forth, there may be multiple examinations of packets between the timea packet is received at the edge of a network, and the time it is routedto a destination. Unfortunately each time a packet is examined andanalyzed there is a delay incurred, which is undesirable, especially forpackets that require quality-of-service, such as packets containingreal-time data such as voice or video.

Presently, there is no flexible way to service different types ofpackets or traffic flows. When a packet enters the edge it is routedthrough a fixed series of vendor's solutions. There is little choice onselecting which services are performed on each packet entering anetwork, regardless of the type of packet. For example, it is difficultfor certain packet types having a higher priority level (or trustedsource) to bypass certain packet analysis equipment to increaseefficiency. It is also difficult to thread (e.g. route) packet flowsthrough different combinations of vendor's devices and services.

Furthermore, much of the functionality provided by different vendorsequipment has fixed functionality limited in scope to particularapplication. Accordingly, while it may be possible to reprogram(upgrade) the particular application for its intended use, it is notpresently possible to dynamically reprogram a device to change itsintended purpose entirely. For example, it is not presently possible toconvert a device for running spyware into a device for performingtranscoding.

Thus, there is presently a desire to more efficiently service packetsentering a network to reduce the quantity of examinations to a minimumdesired level per packet type. There is also a desire to ensure Qualityof Service is not sacrificed with the ability to route certain packetsclassified at the highest priority level through a more efficientexamination process at the edge of a network. Further, there is also apresent desire to simplify and more flexibly integrate the variousdisparate types of functionalities performed at the edge of a network orelsewhere, often provided by different vendors.

SUMMARY

To address the above-discussed deficiencies of the prior art, thepresent invention provides a single network platform that seamlesslyhosts a plurality of disparate types of packet processing applications,where each application may be provided by different vendors. As usedherein a “platform” may include a single physical device, or may includemultiple devices linked together (at one or more sites), butadministered logically as a single network entity.

In one embodiment, the platform includes a plurality of service cardsforming a forwarding plane, each service card configured to execute oneor more particular packet processing applications (applications)associated with performing network security, transcoding, trafficanalysis, or other packet processing functionalities. The platform mayalso include one or more input/output (I/O) cards each card configuredto route the packets from ingress to egress of the platform. Aprogrammable service path structure is included that maps a logical pathfor processing of the packets through one or more of the plurality ofservice cards and one or more of the I/O cards, according tocharacteristics of the packets. Multiple path structures may beprogrammed into the network platform to offer different service pathsfor different types of packets.

In one embodiment, decisions as to how a packet enters or exits theplatform (i.e., forwarding of a packet from the platform) are segregatedfrom decisions as to which applications are traversed (e.g., executed)for processing a packet.

In another embodiment, a fabric is included on the platform having aplurality of input and output ports configured to physically route thepackets from and to one or more plurality of service cards and one ormore I/O cards, according to the programmable service path structure.

In another embodiment, each service card may be reprogrammed dynamicallyduring runtime, such as upgrading an application or completely deletingan application and replacing it with a new application having acompletely new purpose and functionality. For example, it is possible todynamically reconfigure a service card from executing an applicationassociated with performing virus protection to executing an applicationassociated with transcoding.

A feature and advantage of the innovative platform is the ability toincorporate traditional functionality of a router coupled with theability to flexibly integrate multiple network packet serviceapplications, usually found in separate devices.

Additional exemplary implementations and features/advantages aredescribed in the Detailed Description in conjunction with theaccompanying drawings below.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is explained with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Itshould be noted that the figures are not necessarily drawn to scale andare for illustration purposes only.

FIG. 1 illustrates an exemplary environment in which the invention maybe implemented.

FIG. 2 illustrates a packet services platform (platform 106) withinwhich the present invention can be either fully or partiallyimplemented.

FIG. 3 illustrates a logical service path structure for routing packetsby the platform.

FIG. 4 shows another one of a myriad of exemplary logical service pathstructures for routing packets.

FIG. 5 shows another example of a programmable service path structurefor servicing and processing packets.

FIG. 6 shows a chart illustrating various characteristics for packetsand corresponding programmable classifiers and logical paths forservicing the packets.

FIG. 7 shows a logical view for forwarding packets from ingress toegress of a platform that includes load balancing capability.

FIG. 8 shows another logical view of a data path for the flow ofpackets, which is linear.

FIG. 8A shows a logical view of a data path for the flow of packets,which is non-linear

FIG. 8B shows an extensive example of how applications may be linkedtogether using AND and OR operators.

FIG. 9 illustrates a generic platform for implementing a service card,within which aspects of the invention can be either fully or partiallyimplemented.

FIG. 10 illustrates a logical view of a feature server implemented aspart of a control plane for an integrated platform, which includes asandbox.

FIG. 11 illustrates an exemplary method for flexibly routing packetsthrough a platform having disparate network functions.

FIG. 12 is a logical block diagram showing how a control packet flow isrouted to feature servers a control plane, and a data packet flow isrouted to service cards of a forwarding plane.

FIG. 13 shows a programming model of how it is possible to implementuser defined control/management processes in a feature server to accesscore control functions of a platform.

DETAILED DESCRIPTION

Introduction

Reference herein to “one embodiment”, “an embodiment”, “animplementation” or “one implementation” or similar formulations herein,means that a particular feature, structure, operation, or characteristicdescribed in connection with the embodiment, is included in at least oneembodiment of the present invention. Thus, the appearances of suchphrases or formulations herein are not necessarily all referring to thesame embodiment. Furthermore, various particular features, structures,operations, or characteristics may be combined in any suitable manner inone or more embodiments.

In the following description, for purposes of explanation, specificnumbers, materials and configurations are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one skilled in the art that the present invention may bepracticed without each specific example. In other instances, well-knownfeatures are omitted or simplified to clarify the description of theexemplary embodiments of the present invention, and thereby, to betterexplain the present invention.

Exemplary Environment

FIG. 1 illustrates an exemplary environment 100 in which the inventionmay be implemented. Environment 100 includes a first network 102 and asecond network 104. First network 102 and second network 104 arecomputer or telecommunication networks. For instance, in one embodimentfirst network 102 is a core network. A core network typically forms abackbone of a communications network (i.e., service provider) andincludes a combination of high capacity switches and other datatransmission devices.

Whereas, second network 104 is a computer or telecommunication networkthat may be connected to a service provider network, and may havedifferent administrative authorities. For instance, in one embodiment,second network 104 is an access network, which forms a portion of acommunications network which connects users and other networks to firstnetwork 102, and vice versa. In other embodiments second network 104 mayrepresent another core network, or a customer network, such as that of aprivate organization or government entity.

Interposed between first network 102 and second network 104 is a packetservices platform (platform) 106 for routing packets from access network104 to core network 102, and vice versa.

In one embodiment, platform 106 resides at the edge of a network, butcan be located at points within a network other than the edge of anetwork. Platform 106 is used to facilitate communications betweennetworks 102 and 104. For example, in the illustration of FIG. 1,platform 106 provides connectivity access between first network 102 andsecond network 104. Platform 106 may also provide connectivity betweenother core networks or access points.

Platform 106 hosts a plurality of disparate network functionalities in asingle integrated platform. Each of the disparate networkfunctionalities may be selected from different vendors. Examples of thedifferent types of functionality that may be incorporated in platform106 include, but are not necessarily limited to: packet routing,security services (such as firewall(s), Denial of Services detection,malware detection), packet analysis (such as traffic accounting, andflow monitoring), and other present or future packet servicetechnologies.

Thus, platform 106 according to one aspect of the invention includes allthe traditional functionality of a router coupled with the ability toflexibly integrate multiple network packet service applications, usuallyfound in separate devices.

Exemplary Packet Services Platform

FIG. 2 illustrates a packet services platform (platform 106) withinwhich the present invention can be either fully or partiallyimplemented. In one implementation, platform 106 includes a plurality ofservice cards 202(1), . . . , 202(N), input/output cards 206, a fabric208, control elements 212, and feature services 214. The index “N” asused in the figures denotes a number that is equal to or greater than 1.The index N may represent a different quantity of devices per device.For example, N may equal eight with respect to service cards, but mayonly refer to the number two, with respect to I/O cards 206.

The interface between first network 102 and second network 104 isprovided by input/output (I/O) cards 206 for receiving packets fromsecond network 104 and sending the packets to a destination via firstnetwork 102, and vice versa.

Packets may be in the form of data or control packets. As used herein apacket refers to any formatted block of information carried by anetwork. In certain examples herein, the term packet, may refer to asingle packet, packet flows (a collection of packets) or some otherdelineation of one or more packets, such as frames.

Platform 106 generally includes a forwarding plane 201 and a controlplane 203. In general, forwarding plane 201 transports packets andperforms packet processing services associated with the flow of packets.Control plane 103 processes control information for managing andadministering platform 106.

Incoming packets enter ports of I/O cards 206 and are sent to eitherforwarding plane 201 or control plane 203 of platform 106. That is,incoming packets enter I/O cards 206 and are forwarded to one or moreservice cards 202, control elements 212, or feature servers 214, viafabric 208. Incoming packets may also be forwarded directly to anotherI/O card 206 if no additional services are needed, such as for egress.I/O cards 206 generally determine whether packets are sent to eitherforwarding plane 201 or control plane 203 when received by the cards.However, in other implementations, other elements may determine whetherpackets are sent to forwarding plane 201 or control plane 203. Forexample, a service card 202 may perform the function of an I/O card.

Service cards 202 comprise a portion of a forwarding plane for platform106 for processing packets. Each service card 202 includes at least onepacket processing application for performing a packet processingservice. Examples packet processing services include: performing policyenforcement (such as implementing firewall(s), and trafficconditioners), performing intrusion detection and prevention (such asDenial of Services detection, malware detection), performing packetanalysis (such as accounting/metering and traffic monitoring),performing Network Address Translation, transcoding, or other suitablepacket services that may be deployed in a network. Other packetprocessing services may be performed as would be readily appreciated bythose skilled in the art having the benefit of this disclosure.

In one implementation, at least one service card 202 is physicallyimplemented as a slot card, also commonly referred to as a blade orcircuit pack that is processor-based with the ability to execute code,associated with one or more network applications.

It should be appreciated by those skilled in the art after having thebenefit of this disclosure that a service card may take other forms. Forexample, in one implementation, a service card 202 may be implemented infirmware such as using configurable Field Programmable Gate Arrays(FPGAs) and may be reprogrammable.

In still another implementation, a service card 202 may be hardwarebased, such as implemented using Application Specific IntegratedCircuits (ASIC).

Although shown as residing on platform 106, it is appreciated by thoseskilled in the art after having the benefit of this disclosure, that oneor more service cards 202 may be remote from platform 106. For instance,service cards 202 may be multiple hops away from platform 106, and notco-located therein.

I/O cards 206(1) . . . , 206(N), form a portion of the forwarding planefor platform 106. One or more I/O cards 206 are configured to route apacket from ingress to egress of platform 106. That is, each I/O card206 may process an incoming packet received from I/O ports 204 or fabric208, and may send it to an appropriate I/O port 204 for forwarding.

I/O cards 206 may also process an incoming packet previously processedby one or more service cards 202 or other I/O cards 206 via fabric 208.I/O cards 206 process packets, and may make routing decisions includingsuch as determining a next-hop or destination for packets, based onforwarded rules loaded onto I/O cards 206 via fabric 208 by controlelements 212.

Alternatively, in another embodiment, one or more service cards 202 mayform part of the forwarding for platform 106. That is, one or moreservice cards 202 may process packets, and make routing decisionsincluding determining a next-hop or destination for packets, based onrouting rules loaded onto service cards 202 via fabric 208 by controlelements 212. Packets may be forwarded to a next-hop destination via afabric 208, and a port 204 of an I/O card 206.

Although shown as residing on platform 106, it is appreciated by thoseskilled in the art after having the benefit of this disclosure, that oneor more I/O cards 206 may be remote from platform 106. For instance, I/Ocards 202 may be multiple hops away from platform 106, and notco-located therein.

Control elements 212 form a portion of control plane 203 for platform106. Control elements 212 may transmit configuration information forconfiguring service cards 202, and I/O cards 206. Also, feature server214 (to be described in more detail) may transmit configurationinformation to configure service cards 202. Additionally, controlelements 212 may also configure feature servers 214 to install newfeature server applications. Control elements 212 may interact withlogic (not shown) for controlling fabric 208 to effectively establishconnections between service cards 202 and the I/O cards 206. Controlelements 212 may also provide information to service cards 202 forrouting packets within platform 106, referred to as a “programmableservice path structure” (see FIGS. 3-5 to be described). Theprogrammable service path structure may be conveyed to each service card202 via fabric connection 208.

Control elements 212 may also communicate with fabric connection 208 toestablish connections between service cards 202 and I/O cards 206.Control elements 212 maintain knowledge of links status between networkelements (not shown) in network 102, route changes, and updateinformation when changes are made in routing configurations. Controlelements 212 may also provide control for the overall general operationof platform 106.

Although shown as residing on platform 106, it is appreciated by thoseskilled in the art after having the benefit of those disclosure, thatone or more control elements 212 may be remote from platform 106. Forinstance, control elements 212 may be multiple hops away from platform106, and not co-located therein. Accordingly, when platform 106 boots-up(powers-on), platform 106 discovers control elements 112, which becomeassociated with platform 106. In such an implementation, some logic orcontrol unit provides initial direct contact between the data plane andcontrol plane. Further details of how control elements 212 may be boundto forwarding plane 201, such as during boot-up are described incommonly owned U.S. Patent Application Publication No. 20060092974entitled “Softrouter”, which is fully incorporated in its entiretyherein by reference.

It should also be appreciated by those skilled in the art, after havingthe benefit of this disclosure that FIG. 2 illustrates only oneembodiment for implementing control plane 203 for platform 106. Althoughseveral control elements 212 are shown in FIG. 2, it is appreciated thatcontrol plane 203 may only include a single control element.Additionally, some portions of control plane 203 may be implementedremotely as described above, while some portions of control plane 203may reside on the same physical platform as forwarding plane 201. Itshould also be appreciated that forwarding plane 201 and control plane203 are illustrated as being logically distinct from each other, but mayphysically reside and/or operate in an integrated fashion.

Fabric 208 is illustrated as a single block and serves a communicationhub for all elements comprising in platform 106. Fabric 208 may beimplemented as a cross-bar switch, interconnected switches, othersuitable cross-point technology, and a combination of such connectivitytechnology, as would be appreciated by those skilled in the art havingthe benefit of this disclosure.

For instance, in one implementation, fabric 208 may include aninternally contained switched network, such as a Gigabit Ethernetnetwork using several Ethernet switches acting in concert.

Fabric 208 also facilitates multiple parallel communication sessions oftraffic, as well as, permits multiple entities, such as control elements212 and service cards 202, to communicate with each other in asimultaneous fashion. It is noted that while fabric 208 is generallyshown to reside within a single platform or chassis, it is possible thatone or more portions of fabric 208 may be distributed across a networkat different sites and linked together forming a single mass fabric.

As shall be explained, the intra-routing of packets (i.e., the pathstructure) within platform 106 is programmable. That is, the exact orderof servicing packets by service cards 202 is completely configurable.Thus, platform 106 facilitates the integration of functions provided byeach service card 202 into programmable combinations of one or moredifferent services, each such combination of services performed onincoming packets based on characteristics of the packets.

Exemplary Programmable Service Combinations

FIG. 3 illustrates a logical service path structure 302 for routingpackets by platform 106. Logical service path structure 302 maps alogical path for processing of a packet through one or more of aplurality of service cards 202 according to characteristics of a packetreceived by platform 106.

In the illustrated example, a packet is received at an ingress port byI/O card 206(1) and forwarded to service card 202(2) via fabric 208,according to logical service path structure 302. The packet is processedby at least one application 222 associated with a service card 202(2),and forwarded to a next service card 202(3). Next, the packet isserviced by at another application 222 on service card 202(3), andforwarded to I/O card 206(2), in accordance with logical service pathstructure 302. Finally, the packet is forwarded to first network 104 orsecond network 102 via an egress port 204 of I/O card 206(2).

FIG. 4 shows another one of a myriad of exemplary logical service pathstructures (e.g., service path structure 402) for routing packets byplatform 106. In this example, according to service path structure 402 apacket flow is serviced by application 222 on service card 202(1), andthen skips service cards 202(2) and 202(3), prior to egress port 204 viaI/O card 206(2).

FIG. 5 shows another example of a programmable service path structure502 for servicing and processing packets by platform 106. In thisexample, there may be multiple discrete applications 504(1), 504(2), and504(3) available on a service card 202(1) for processing packets. Eachapplication 504 has the capability to perform a class of processingdirectly to, or associated with a packet. In one implementation, eachclass of processing associated with an application is typically loadedas discrete code into a service card 202.

As shown in FIG. 5, when transporting a packet from ingress to egress ofa platform 106, programmable service path structure 502 is configured toselect and link one or more applications 504(1), and 504(3) together.Programmable service path structure 502 is also configured to bypass oneor more applications, such as application 504(2), when a packettraverses service card 202(1).

Thus, a service card 202(1) may contain multiple applications 504 andeach of these particular applications may be selected or bypassed inaccordance with programmable service path structure 502.

It is noted that while the above example only shows three networkservice applications, it should be appreciated by those skilled in theart after having benefit of this disclosures that a service card mayinclude more or less applications.

FIG. 5 also shows that a service card, or a network function implementedon a service card, such as by service card 202(2) may provide I/Ofunctionality with the ability to select next-hop destinations forpackets or packet flows.

Thus, based on the examples of FIGS. 3, 4 and 5, it should be apparentto those skilled in the art that the logical path (i.e., a programmableservice path structure) that each packet flow takes when traversingthrough platform 106 may be programmed into platform 106. Thus, FIGS. 3,4, and 5 show logical paths for processing a packet flow from ingress toegress platform 106.

In order to link the completion of an application performed in a servicecard 202 to the start of another (in the same card or on a differentcard), a message system may be utilized to transport packets,facilitating a packet flow through platform 106.

In one implementation, the message system uses a service path flow-ID (apointer to the next module, I/O card, or port), which is looked-up by aservice card indicating a next hop for a packet flow. A next hop ID isthen encoded into a header of a packet flow, indicating its nextdestination. Accordingly, each sub-path (e.g., segment) of aprogrammable service path structure provides the information necessaryto link the next service card 202 or a series of service cards 202 forservicing a packet.

In another implementation, an entire sequence of service cards 202 andapplications forming a programmable service path structure may bedetermined upon ingress of packets to platform 106. In such a scenario aflow ID may be embedded in the header(s) of a packet indicating whichservice flow (path/sub-paths) to take. In such an implementation, I/Ocards 206 may determine appropriate service cards 202 which trafficshould be directed when the packets are first received. Multiplesequential applications to perform a sequence of services and functionsmay be performed using service cards 202 which may be daisy chainedtogether through connections established via fabric 208.

In another implementation, characteristics of the packets may be used todetermine which sequence of service cards 202 comprising a logicalservice path structure is chosen for routing a packet flow throughplatform 106.

FIG. 6 shows a chart illustrating various characteristics for packetsand corresponding programmable classifiers and programmable service pathstructures for servicing the packets.

For instance, suppose packets of a characteristic type A have aclassifier X encoded therein which determines which one of a pluralityof programmable service path structures (i.e., Service Path 1, ServicePath 2, Service Path 3, . . . , or Service Path N) a packet flow is tofollow. Each programmable service path structure contains a sequence ofapplications which may include one or more service cards 202 as well asapplications per module. Suppose the programmable service path structurecorresponding to classifier X is Service Path 1. Further suppose thatthe programmable service path structure for Service Path 1 includesservice application 1 (a firewall), service application 2 (virusdetection) and then an I/O card 206 (routing). This logical path couldbe programmed into I/O cards 206 and service cards 202, such that anypacket received with classifier X causes the I/O cards 206, and servicecards 202 to forward each packet according a programmable service pathstructure corresponding to Service Path 1.

FIG. 7 shows a block diagram of a sample programmable service pathstructure that may include two different Service Paths: Service Path 1or Service Path 2.

Characteristics that may be utilized to determine how a packet is routedthrough platform 106 include the source of the packets, whether thesource is trusted or not, the type of packets (i.e., data, control,video, etc.), the quality-of-service associated with the packets, and soforth. Any characteristic associated within a packet such as a fieldwithin its header or data associated with a payload, may be used todetermine which service path is selected (Service Path 1, Service Path2, . . . , or Service Path N,).

Thus, in a path routing implementation, an entire sequence ofapplications embedded on one or more service cards, and I/O cards, isselected upon entry to platform 106 using a flow classifier.

In another implementation, the programmable service path structure maybe dynamically determined on-the-fly. That is, a next hop withinplatform 106 is determined anew after each I/O card or service cardusing packet classifications. For example, a service card may select oneof two different service cards to distribute traffic if either suchcards were included as part of a next-hop.

In another embodiment, a service card 202 may also determine whichprogrammable service path a packet flow is to follow based oncharacteristics of the packets.

FIG. 7 shows a logical view for forwarding packets from ingress toegress of platform 106 that includes load balancing capability. In thisexample, packets may either follow service path 1 or service path 2,based load balancing of traffic flow. Each service path includes one ormore applications for processing packets.

A programmable service path structure may be linear, such as shown FIG.8, in which a first service application is executed, followed by asecond subsequent service application, followed by a next serviceapplication, and so forth, until all service applications are executedwithin a service path structure. Furthermore, each one of theapplications 1, 2, 3, . . . through N, forming the programmable servicepath structure, is configurable and reconfigurable. Differentapplications can be added or removed from the service path simply byre-programming/re-configuring one or more of the I/O cards, the servicecards through the control plane.

A programmable service path structure may also be non-linear such asshown in FIG. 8A. “AND” and “OR” operators are primitives that may beused by programmers/users to construct a logical service path structureand link different applications. In particular, the AND operatorreplicates packet flows. For instance, with use of an AND operator inFIG. 8A, packet flows would be duplicated for applications 2 AND 3. Inother words, if a packet flow is to be replicated, meaning creating twoor more copies, one copy of the packet flow will follow the upper pathto application 2, and one duplicate copy of the packet flow will followthe lower path to application 3.

Whereas, the OR operator selects a particular one of at least twosubpaths. In particular, with use of an OR operator in FIG. 8A, packetflows would either be sent to application 20R application 3, such as forload balancing.

Thus, using the basic flow operators AND and OR, it is also possible tologically link a next application with a prior application by insertingeither operator between applications to provide a link.

It is noted that when there is only one branch, the AND or OR operatorsmay be used as links between applications in a linear fashion. Thus,referring back to FIG. 8, each application 1, application 2, . . . ,application N, may be linked together using the AND or OR operators.Thus, AND or OR operators may link multiple branches.

FIG. 8B shows a more extensive example of how applications may be linkedtogether using AND and OR operators. Once a structure is defined itneeds to be mapped to into the physical implementation. That is, thestructure of FIG. 8B is a logical structure showing how the serviceapplications are linked. Once this logical structure is developed, it ispossible to map the logical structure into platform 106 by installingdifferent applications onto service cards 102, and creating a pathrouting structure using the OR and AND operators.

In one embodiment, it is also possible to include external devices orfunctions within the service path structure that my not be integratedinto platform 106. It is possible to define a service path structurethat flows through one or more I/O cards 106 and service cards 102, thenflows out of platform 106 to an external device, which processes thepackets. After the external device processes the packets, they are sentback to platform 106, and the packets continue to be processed by theservice path structure until they exit platform 106. Thus, a servicepath structure may include external elements, which may be connected toI/O ports of an I/O card or service cards with external ports to handoffpackets to an external device.

Exemplary Computing Platform for Service Card

FIG. 9 illustrates a generic platform for implementing a service card202, within which aspects of the invention can be either fully orpartially implemented. As mentioned above, each service card istypically a computing device, such as a blade, or a circuit board.However, service card 202 may be other general or special purposecomputing devices.

In one embodiment, service card 202 includes at least one processor 904,and memory 908. Memory 908 may include volatile memory (e.g., RAM)and/or non-volatile memory (e.g., ROM). In some implementations,volatile memory is used as part of the computing device's cache,permitting application code and/or data to be accessed quickly andexecuted by processor 904. Memory 908 may also include non-volatilememory in the form of flash memory, content addressable memory and soforth. It is also possible for other memory mediums having variousphysical properties to be included as part of service card 202.

A service card 202 can also contain other specialized other hardwareassist devices (not shown). For example, it may include a specialpurpose processor (not shown) that can perform security functions suchas encryption/decryption, or payload search engines, in conjunction witha general purpose processor.

Operating system 922 may reside as a component in the form ofcomputer-executable instructions and/or logic within memory 908, and mayinclude a file system that when executed serves as a logical interfacebetween code stored in memory. In one implementation, operating system922 is the Linux Operating System permitting a completely open platform.Other operating systems may be incorporated into a module 202 as wouldbe appreciated by those skilled in the art having benefit of thisdisclosure.

Service card 202 may also include one or more Input/Output ports 916 totransmit and/or receive data. I/O ports 916 are typically connected insome fashion to controller 902 (processor 902 and memory 908). I/O ports916 are usually at least partially implemented in hardware forconnecting computing device 900 to a communication link 918, and mayinclude wired as well as wireless capabilities. Communication link 918may include any suitable connection means for handling thetransportation of data to and from service card 202, such as, but notlimited to, cable, fiber optics, and wireless technology. Communicationlink 918 may also include connectors to/from a backplane or faceplate(not shown) of platform 106.

Stored within one or more portions of memory 908 is a service engine950. That is, service engine 950 includes one or more sets ofcomputer-executable code resident on a computer-readable medium (such asmemory 908). Service engine 950 performs functions associated with oneor more service applications 956 as mentioned above. Each one of theservice applications 956 may be programmed and reprogrammed to performvarious packet services.

Service engine 950 may also include application and configuration data958, such as flow-look up tables used for purposes of choosing a nexthop or next point to route packets.

In one implementation, service engine 950 may also include acommunications module 970, which is a set of code associated with thecommunicating between control elements. In one implementation,communications module 970 may include a standard protocol such as“ForCES” for communicating with control elements. Other communicationprotocols could be incorporated in module 202, as would be appreciate bythose skilled in the art after having the benefit of this disclosure.

Although described in terms of code, the exemplary service engine 950may be implemented in hardware, software, or combinations of hardwareand software. Additionally, all components of service engine 950 may becommunicatively coupled to each other. As would be appreciated by thoseskilled in the art, many of the components of service engine 950 may bestored and identified as files under control of operating system 922.

In other embodiments, service cards 202 may be implemented as FieldProgrammable Gate Array (FPGA), ASIC, network processors, or anycombination of the above.

Exemplary Extensible Data Planes

Referring back to FIG. 2, much functionality associated with platform106 is implemented in software which further facilitates reconfigurationand scalability. For example, the quantity of service cards 202, and I/Ocards 206 per platform 106 may vary. Additionally, service cards 202, orI/O cards 206 may be added (or removed) as necessary, and fabric 208 isreconfigurable to accommodate the necessary connections. As describedabove, it is possible to configure and reconfigure service cards 202,I/O cards 206, and fabric 208 to establish the appropriate connectionsin a dynamic fashion. All such configurations can be loaded in theirrespective devices via control elements 212 (FIG. 2).

In terms of control, a plurality of control elements 212 can beimplemented remotely for platform 106 and/or internally within platform106. Forwarding plane 201 may logically communicate with controlelements 212 as single virtualized unit, as it may not be aware of eachindividual control element 212. This makes it possible to scale-up andincrease the capacity of control plane 203 with more control elements212 as forwarding plane 201 logically treats control elements as asingle virtualized control plane.

Thus, in addition to providing scalability for the forwarding plane 201platform 106 provides scalability for the control plane 203. Inparticular, the number of control elements may vary, and additionalcontrol elements 212 can be added without platform 106 knowing there isany change, as control elements 212 as a cluster can be virtualized.

The available processing of control elements 212 may cooperate with eachother to share the processing burden of the control plane as necessary.As such, the processing capability afforded by the control plane ofplatform 106 may be scaled throughout the life of platform 106 by addingcontrol elements 212, which increases control processing resources forthe forwarding elements.

Based on the foregoing, platform 106 provides scalability in anindependent fashion from the control plane and the forwarding plane,including scalability for I/O. Depending on the control plane andforwarding plane resources, as well as the number of I/O cards andassociated ports, fabric 208 can be configured dynamically toaccommodate additional service cards 202, or I/O cards 206.

As fabric 208 is implemented using a switched network (gigabitEthernet), it supports simultaneous communications, without requiringthe respective communicating entities to wait for network availabilityprior to communicating with each other. Thus, the connections betweenmodules are not fixed and are effectively under software control,thereby avoiding physically static connections. Platform 106 asimplemented will include an appropriate backplane for facilitating theconnection of each of the elements described above, as would be readilyappreciated by those skilled in the art having the benefit of thisdisclosure.

Exemplary Extensible Control Plane

As control elements 212 may be implemented in a virtual fashion, it ispossible to deploy new service functionalities executed by featureservers 214, in a sandbox.

FIG. 10 illustrates a logical view of a feature server 214 implementedas part of control plane 203 for platform 106, which includes a sandbox1004. Sandbox 1004 allows service functions to be carried out inside aprotected environment which is partitioned from data and code residingin memory. As all code is executing in a restricted environment, whichprotects code and data stored in memory used by control plane 203 aswell as forwarding plane 201.

In one implementation, feature server 214 includes a sandbox 1004, whichis a partitioned area of memory in which code 1006 created by anend-user is installed. Sandbox 1004 is an area of memory in the controlplane that is segregated from other areas of memory in which trustedapplication code or operating system code resides. Sandbox 1004 createsan environment in which there are strict limitations on what systemresources the code created by a user can request or access. A securitymanager 1008 implemented in software guarantees that no run-timeenvironment is replaced by the code in sandbox 1004, which has accessthrough a well defined Application Programming Interface (API). Securitymanager 1008 also blocks any operations in which it is possible toperform a dangerous operation which could cause harm to the system.Security manager 1008 has the option to veto the operation by generatinga security exception.

In another embodiment, a sandbox can be defined for each application.That is, there may be different sandboxes for each service application.

More specifically, a feature server 214 implemented with customerimplemented application may directly access an existing control state ofplatform 106 in a safe and efficient manner. The safety offered by afeature server 214 is guaranteed through use of a restricted functionalAPI and the use of logical or physical sandboxes 1006.

Exemplary Method of Securing Data

FIG. 11 illustrates an exemplary method 1100 for flexibly routingpackets through a platform 106 having disparate network functions.Method 1100 includes blocks 1102, 1103, 1104, 1105, 1105A, 1106, and1108, (each of the blocks represents one or more operational acts). Theorder in which the method is described is not to be construed as alimitation, and any number of the described method blocks can becombined in any order to implement the method. Furthermore, the methodcan be implemented in any suitable hardware, software, firmware, orcombination thereof.

In block 1102, a data packet is received by platform 106. For example, apacket is received at ingress port of platform 106 (FIG. 2).

In a decisional block 1103, a determination is made whether the packetis a control or data packet. If in block 1103, the incoming packet isdetermined to be a control packet, process 1100 proceeds to block 1105.In block 1103, the packet is routed to one or more feature servers orcontrol elements.

On the other hand, if in block 1103, the incoming packet is determinedto be a data packet, process 1100 proceeds to block 1104. In block 1104,a characteristic of the packet is determined based on header or payloadinformation.

Additionally, it is possible for platform 106 to originate packets, suchas packets originating from control elements 212 or feature server 214,based on packets received in block 1102. Accordingly, in block 1105A, apacket may originate from control elements or feature servers.

In block 1106, a flow-ID is inserted in the header of a packet relayinginformation indicating which service path (or next hop—i.e., sub-path)of a logical service path (full path) the packet is to follow. Thislogical path may be selected from one out of a plurality of differentservice paths, which are configurable and reconfigurable. Each flow-IDis configured to link a completion of processing of one specific segmentof processing associated with one of the service cards (serviceapplications) to a start of processing of another specific segment ofanother of the service cards such that each portion of processing of thepackets can be performed in a specific order and by any of the pluralityof service cards specified by the plurality of service paths. The packetis routed to service cards in accordance with the logical path selected,and each service application is executed.

In block 1108, the packet is routed from a service card to an I/O card,which is configured to route the packet to a port for egress of thepacket out of the platform. The flow-ID or some other pointer, ormessage may be used to link the service path with the data card forrouting of the packet to the data card.

It is should be appreciate by those skilled in the art having thebenefit of this disclosure that certain operational acts of method 1100may be performed differently. For example, it may not be necessary toinsert flow-ID into the packets to select a service path. Instead, eachservice card may be configured to selected a next-hop or service chainbased on characteristics of the payload or header associated with apacket. Additionally, one or more service cards may have dedicatedtables for determining a next-hop of a packet. Still further informationinserted in field headers without adding additional bits that may berelied on to select a service path.

Additionally, any exemplary functionality provided by a service card,logical path or functional block may be described in the general contextof computer-executable code being executed by a processor of a computer.Generally, computer-executable code include modules, routines, programs,objects, components, data structures, logic, and other executable codethat perform particular tasks or implement particular abstract datatypes when executed by a computing device. Computer-executable code maybe located in a computer-readable-medium, such as but not limited to,local, remote, and/or distributed computer storage media includingmemory storage devices.

FIG. 12 is a logical block diagram showing how a control packet flow isrouted to feature servers 214, and a data packet flow is routed toservice cards 202 of forwarding plane 201.

FIG. 13 shows a programming model of how it is possible to implementuser defined control/management processes in a feature server 214 toaccess core control functions of platform 106, such as control elements212. A feature server 214 may also communicate with a service card 202in the forwarding plane 201. A feature server also allows extension ofthe control function of platform 106 to permit a customer to add its ownvalue-added features to applications. Some examples of such value addedfeatures include: customer routing, custom protocol processing, customnetwork measurement, custom data management

Custom Routing—

standard shortest path routing as commonly used in IP routing may not besuitable for certain applications. For example, VoIP should be routedalong a least delay path rather than a shortest path. In general, acarrier (or its customers) may have its special routing requirementsthat do not mesh well with traditional protocols. Force fitting of suchrouting requirements on a shortest path routing framework can beunwieldy. The ability to host custom routing protocol can solve thisproblem. With this, a customer can deploy its own version delay-basedrouting and even inter-domain QoS routing with its peers.

Custom Protocol Processing—

The emergence of IPTV has brought renewed attention to IP multicast. Akey challenge to IPTV is the ability to perform fast channel change.This is typically implemented as multicast group join and leave, whichin turns relates to IGMP processing. Specialized IGMP processing canprovide a customer unique differentiation to its IPTV network.

Custom Network Measurement—

Basic network measurements provide statistics only at the transportlevel, e.g., queue length, link utilization, etc. A carrier canindirectly infer the performance of an application using these measures.A way to understand application performance is to directly measure it atthe application level. For example, with an extended control plane, itis relatively easy to inject VoIP signaling or bearer traffic todirectly measure SIP signaling and VoIP quality.

Custom Data Management—

A router collects a lot of internal statistics. The existing way ofgetting at this statistics is clumsy and inefficient. For example, SNMPis very inefficient if you try to obtain the data at a differentgranularity. Through feature servers, data can be preprocessed (e.g.,aggregated) within platform 106 and exported in a customize format.

It is to be understood that the present invention is not limited to theembodiments described above, but encompasses any and all embodimentswithin the scope of the subjoined Claims including their equivalents.

What is claimed is:
 1. A system for processing a packet, comprising: aplurality of service applications, each configured to perform a specificsegment of processing on the packet; a plurality of service paths,programmably configured to link a completion of processing of onespecific segment of processing associated with one of the serviceapplications to a start of processing of another specific segment ofanother of the service applications such that each portion of processingof the packet can be performed in a specific order and by any of theplurality of service applications specified by the plurality of servicepaths; a plurality of input/output (I/O) cards, each I/O card configuredto route packets from an ingress or to an egress of the system, whereinat least one of the plurality of service paths provides a link betweenat least one of the plurality of service applications with at least oneof the plurality of I/O cards; and a control plane including at leastone feature server configured to execute one or more customer-configuredapplications and to modify at least one of the plurality of servicepaths.
 2. The system as recited in claim 1, wherein at least onespecific segment of processing on the packet includes executing anapplication associated with network security comprising at least one ofa firewall process, a Deep Packet Inspection process, a virus detectionprocess, and a denial of service detection process.
 3. The system asrecited in claim 1, wherein at least one specific segment of processingon the packet includes executing an application associated with trafficaccounting/monitoring.
 4. The system as recited in claim 1, wherein thespecific order and the plurality of service applications specified bythe plurality of service paths are determined based on at least oneidentified characteristic of the packet.
 5. The system as recited inclaim 1, further comprising a plurality of service cards, eachconfigured to execute at least one of the service applications.
 6. Thesystem as recited in claim 5, wherein at least one of the service cardsand/or I/O cards is configured to identify at least one characteristicof the packets, and based on the identified at least one characteristic,assign a classifier to the packets which is used to navigate the packetsthrough the programmable service path structure.
 7. The system asrecited in claim 5, wherein at least one of the service cards and/or I/Ocards is configured to route packets to a next destination.
 8. Thesystem as in claim 1, further comprising a forwarding plane, theforwarding plane controlling one or more portions of the programmableservice path structure.
 9. The system as recited in claim 8, wherein theleast one feature server is used in conjunction with the forwardingplane for executing an application associated with at least one of abandwidth management and a traffic management process.
 10. The system asrecited in claim 8, wherein the at least one feature server is used inconjunction with the forwarding plane for executing an applicationassociated with at least one of a content adaptation process and anapplication acceleration process.
 11. The system as recited in claim 1,wherein at least one of the plurality of service applications isdynamically reprogrammable.
 12. The system as recited in claim 1,wherein at least one of the plurality of service paths is dynamicallyreprogrammable.
 13. The system as recited in claim 1, wherein at leastone of the customer-configured applications is accessible from memory byan Application Programming Interface.
 14. The system as recited in claim1, wherein at least one of the customer-configured applications issegregated from other areas of memory by a logical or physical sandbox.15. The system as recited in claim 1, wherein the customer-configuredapplications are dynamically loadable or reprogrammable.
 16. The systemas recited in claim 1, wherein the at least one feature server isconfigured to access a system state of the system via an ApplicationProgramming Interface.
 17. The system as recited in claim 1, wherein thecontrol plane includes at least two feature servers configured tocooperate when performing load-balancing of packet traffic.
 18. Thesystem as recited in claim 1 comprising a fabric for providing theplurality of service paths, wherein the control plane includes aplurality of control elements configured to communicate with the fabricand wherein at least one of the control elements and the at least onefeature server is configured to cooperate with each other to shareprocessing of the control plane.
 19. The system as recited in claim 18,wherein when a control element or a feature server is added to thesystem the fabric is adapted to dynamically establish desiredconnections between the fabric and the control element or the featureserver added.
 20. The system as recited in claim 18, wherein the controlelements and the at least one feature server are configured to cooperatewith each other to share processing of the control plane, and areconfigured to logically communicate with a forwarding plane as a singlevirtualized unit.
 21. The system as recited in claim 20, wherein thecontrol elements are remote from the service cards and communicate withthe service cards using a “ForCES” communication protocol.
 22. A systemfor processing a packet, comprising: a forwarding plane including aplurality of service cards, each service card configured to execute atleast one of a plurality of service applications to perform at least onespecific segment of processing on the packet; a plurality of servicepaths, programmably configured to link a completion of processing of onespecific segment of processing associated with one of the serviceapplications to a start of processing of another specific segment ofanother of the service applications such that each portion of processingof the packet can be performed in a specific order and by any of theplurality of service applications specified by the plurality of servicepaths; a plurality of input/output (I/O) cards, each I/O card configuredto route packets from an ingress or to an egress of the system, whereinat least one of the plurality of service paths provides a link betweenat least one of the plurality of service applications with at least oneof the plurality of I/O cards; and a feature server configured toexecute one or more customer-configured applications and to modify atleast one of the plurality of service paths.
 23. The system as recitedin claim 22, wherein at least one specific segment of processing on thepacket includes executing an application associated with networksecurity comprising at least one of a firewall process, a Deep PacketInspection process, a virus detection process, and a denial of servicedetection process.
 24. The system as recited in claim 22, wherein atleast one specific segment of processing on the packet includesexecuting an application associated with traffic accounting/monitoring.25. The system as recited in claim 22, wherein the specific order andthe plurality of service applications specified by the plurality ofservice paths are determined based on at least one identifiedcharacteristic of the packet.
 26. The system as in claim 22, furthercomprising a control plane, the control plane controlling one or moreportions of the programmable service path structure.
 27. The system asrecited in claim 22, wherein at least one of the service cards and/orI/O cards is configured to identify at least one characteristic of thepackets, and based on the identified at least one characteristic, assigna classifier to the packets which is used to navigate the packetsthrough the programmable service path structure.
 28. The system asrecited in claim 22, wherein at least one of the service cards and/orI/O cards is configured to route packets to a next destination.
 29. Thesystem as recited in claim 22, wherein the feature server is used inconjunction with the forwarding plane for executing an applicationassociated with at least one of a bandwidth management and a trafficmanagement process.
 30. The system as recited in claim 22, wherein thefeature server is used in conjunction with the forwarding plane forexecuting an application associated with at least one of a contentadaptation process and an application acceleration process.
 31. Thesystem as recited in claim 22, wherein at least one of the plurality ofservice applications is dynamically reprogrammable.
 32. The system asrecited in claim 22, wherein at least one of the plurality of servicepaths is dynamically reprogrammable.